Update OkHttp to h2-16. #3
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Contributor
|
See #2 |
Member
|
And since #2, some teams internally have been pushing to use a stable version of OkHttp (so 2.1.0) in order to reduce their risk, which would actually mean downgrading to h2-14. I do get a distaste in my mouth when talking about limiting what version of libraries we are on due to internal issues, but right now it doesn't seem to really matter. If it does start to matter, I can make some code rewriting scripts to let us diverge. Do note that it isn't all bad, because gRPC pushing the envelope caused me to upgrade people off of OkHttp 1 and keep the version of OkHttp recent. |
songy23
pushed a commit
to songy23/grpc-java
that referenced
this pull request
Oct 31, 2017
Resolve conflicts in core
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.